Automated role adjustment in a computer system

ABSTRACT

An embodiment of the invention is associated with a system having a role for controlling user access, the role comprising users, permissions, and a set of rules. The embodiment records each of a succession of access events in an access log, each event comprising an instance of the system being accessed by a user. The embodiment further analyzes recorded access events in the access log at selected time intervals, to detect a condition or violation of rules of the set of rules. Responsive to detecting a condition or violation, the embodiment selectively determines whether any change to the users or permissions of a specified role is needed. Each needed change is then implemented.

BACKGROUND

1. Field

The invention disclosed and claimed herein generally pertains to asystem and method for automated adjustment of roles used to control orregulate computer system access. More particularly, the inventionpertains to a system and method of the above type wherein an access logis maintained, and is periodically or aperiodially used in determiningwhether a particular role needs to be refined or adjusted.

2. Description of the Related Art

Inaccurate, obsolete or overly generous (or overly provisioned)authorizations to access a computer system can create significantsecurity risks. Such authorizations can possibly cause malicious dataleakage or program execution. In an ideal arrangement, only those userswho have a current business requirement to access a given set ofresources should possess the respective authorizations which allow themto do so. However, maintaining precise authorizations, particularly invery large IT environments comprising millions of users and permissions,exceeds the capacity of many manual or semi-automated security processesthat are currently being used.

Role-based access control (RBAC) is an access policy which is presentlyused in commercial and other applications and systems. Access in RBAC iscontrolled at the system level, outside of the user's control. An RBACconfiguration controls collections of permissions that may includecomplex operations, such as e-commerce transactions, but may alsocontrol simple operations, such as read or write operations. A role inRBAC generally comprises a set of permissions and a set of users.

While proper RBAC roles match a job function, and job functionstypically change only slowly over time, ongoing changes still do occurin both the Information Technology (IT) environment and the personnel ofan organization. For example, servers can be decommissioned and newservers can be added or introduced. Organization employees come and go.These natural changes are likely to result in RBAC states becomingobsolete or non-optimal, over time. Accordingly, in order to account forthese changes, roles that are initially defined and deployed in an RBACsystem should thereafter be assessed and certified, at specified timeintervals. Any needed changes to the role structure would also need tobe approved.

At present, role certifications tend to be time-consuming and tediousfor approvers. Also, roles frequently have excessive access privileges,and the human eye generally does not detect “drift”, or unusedpermissions and dormant users. Moreover, it is anticipated that futureaccess control systems will increasingly rely on analyticalcapabilities.

SUMMARY

Embodiments of the invention provide a method, system and computerprogram product for monitoring the constituent parts of a role of theabove type, i.e., role users and role permissions, with regard to recentor current usage. This monitoring effort determines a need for roleimprovements, which may either be performed directly by the monitor, orproposed to an administrator in the form of a warning or recommendation.Thus, these embodiments allow roles to be automatically adapted andrefined over time, resulting in lower administrative costs, improvedsecurity and reduced audit failures.

An embodiment of the invention directed to a computer implemented methodis associated with a computer system wherein a specified role controlsuser access, the specified role comprises one or more users and one ormore permissions, and a set of prespecified rules pertains to thespecified role. The method includes the step of recording access datapertaining to each of a succession of access events in an access log,wherein each event comprises an instance of the computer system beingaccessed by a particular user. The method further includes analyzingrecorded data contained in the access log at selected time intervals, inorder to detect one of a plurality of prespecified conditions.Responsive to detecting a prespecified condition, the method selectivelydetermines whether any change to the users or to the permissions of thespecified role is needed. The method further includes implementing eachneeded change to the users or to the permissions.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram showing components configured for implementingan embodiment of the invention.

FIG. 2 comprises a flowchart showing steps for a method comprising anembodiment of the invention.

FIG. 3 comprises a flowchart showing further steps for a methodcomprising an embodiment of the invention.

FIG. 4 is a block diagram showing certain components of FIG. 1 infurther detail.

FIG. 5 is a schematic diagram illustrating role hierarchies.

FIG. 6 is a flowchart illustrating a dormant user algorithm that can beimplemented in an embodiment of the invention.

FIG. 7 is a flowchart illustrating an unused permission algorithm thatcan be implemented in an embodiment of the invention.

FIG. 8 is a block diagram showing a network of data processing systemsin which an embodiment of the invention may be implemented.

FIG. 9 is a block diagram showing a computer or data processing systemthat may be used in implementing embodiments of the invention.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

Referring to FIG. 1, there is shown a system 100 comprising anembodiment of the invention. System 100 includes a role optimizationmonitor and management component 102, also referred to herein as a roleoptimization manager (ROMM) for convenience. ROMM 102 directs or managesa process carried out by system 100 that automatically reduces theadministrative burden of maintaining and updating security rolesrequired for one or more computer systems, wherein the roles areprovided or defined in accordance with an RBAC policy. ROMM 102 alsomonitors the usage of users and permissions associated with such roles,at prespecified time intervals.

More particularly, the process of system 100 enables respective roles tobe tuned, in order to authorize only the least or minimum accessprivileges that are required for operation of a given computer system,or access control system. System 100 also notifies administrators ofrole drift, or changes that impact role quality, and proposesmodifications in response to the role drift. Moreover, system 100provides a platform for collecting and using relevant statistical data,as described hereinafter in further detail.

Referring further to FIG. 1, there is shown an identity and accessmanagement component 104. This component enables a user to log into eachof two or more disparate computer systems, wherein access is authorizedin accordance with the RBAC policy. Thus, the user can access a system,if she or he is included in a role that provides permission for suchaccess. Access control systems 106 and 108 exemplify different computersystems, wherein system access roles and permissions are furnished orprovisioned to users by access management component 104.

FIG. 1 further shows an access log repository 110, which contains anaccess event log for each access control system such as system 106 or108. Whenever one of these systems is accessed by a user, based on apermission provided by a role, certain information is entered into theaccess event log for that system or resource. The entered informationcan include a timestamp at the beginning of the access event, and theidentity of the user. Further information may include the associatedsystem and resource, the status thereof and the action taken.

In addition to resource access events, log repository 110 contains ahistorical record showing the activations of respective roles andpermissions, which are authorized by the RBAC policy. Recorded roleactivation data may include activation timestamp, user, role andpermission identities, the associated access control system, andtermination timestamp. Access log repository 110 performs the furtherfunction of aggregating log data from a multitude of access controlsystems.

In carrying out its objectives as described above, system 100 moreparticularly identifies certain conditions. System 100 also proposes orperforms tasks to address these conditions, in order to improve rolequality. These conditions may include, without limitation, (1) Valid andDormant users, (2) Superfluous permissions, (3) Role size, (4) Dormantroles, (5) Role risk, (6) Role concurrency, and (7) permission-basedseparation of duties. These conditions are respectively defined asfollows:

-   -   (1) Valid and Dormant users: users who are either no longer        valid (e.g., lack employee verification) or have not activated a        role for a time interval are candidates for being removed from        the role or being assigned a new role, possibly arranged in an        inheritance relationship with the original role,    -   (2) Superfluous permissions: permissions may not have been        exercised for a given time and thus represent excessive        privilege. Such permissions should be removed from the role or a        new role should be created and arranged in an inheritance        hierarchy with the original one.    -   (3) Role size: identify roles exceeding lower or upper bounds        for the cardinality of users or permissions as per best        practice, often referred to as cardinality constraints.    -   (4) Dormant roles: roles which have not been activated for a        given time interval. Dormant roles are a special case of dormant        users, where all role members are dormant.    -   (5) Role risk: if metadata is available about the sensitivity of        the resources being accessed, the role can be evaluated with        regards to the consistency of its permissions, e.g., highly        sensitive resources may belong in a separate role instead of        being mixed in the same role with low-sensitivity permissions.    -   (6) Role concurrency: The maximum number of concurrent sessions        for a role. Identifying the maximum number of concurrent role        sessions helps to define cardinality constraints supported by        some RBAC systems.    -   (7) Permission-based separation of duties: Given sets of        permissions which should be mutually exclusive, identify        accesses where users each accessed sets of one or more mutually        exclusive permissions. This is helpful for RBAC environments        which support only user-based separation

In order to accomplish its respective tasks, FIG. 1 further shows system100 provided with an RBAC state repository 112, a statistics database114, a user registry 116, and a monitoring policy repository 118.Repository 112 provides a location for storing current data pertainingto the roles and permissions assigned to users of respective accesscontrol systems, such as systems 106 and 108, in accordance with theRBAC policy.

In its operation, ROMM 102 exchanges information with repositories 110,112 and 118, and also with registry 116. ROMM 102 uses such informationto modify and refine roles over time. ROMM 102 also provides informationpertaining to certain roles to access management component 104, such asrecommendations, warnings, notifications and updates in regard thereto,over a link 120.

As ROMM 102 processes data pertaining to respective roles, statisticaldata for further role analysis is collected and updated in statisticsdatabase 114. Examples of such statistical data include but are notlimited to usage frequencies, role activations, permissions accessed androle size. The statistics database provides measures for specifiedanalytics applications, exemplified by applications for reports, machinelearning, IT security risks and OLAP multidimensional visualization.

User registry 116 provides a list of users of systems such as systems106 and 108. Repository 118 contains policies pertaining to theoperation of ROMM 102.

Referring to FIG. 2, there is shown a flowchart that includes steps fora method comprising an embodiment of the invention. More particularly,the flowchart of FIG. 2 is directed to assessing the conditions (1)-(4)described above, in connection with a system using an RBAC policy foraccess security, and for implementing corrections found to be necessary.Steps of FIG. 2 may be carried out by ROMM 102 and other components ofsystem 100, but embodiments of the invention are not limited thereto.

Upon starting the method of FIG. 2, information pertaining to each ofthe roles of the particular policy is acquired at step 202. Suchinformation could, for example, be obtained by ROMM 102 by accessingRBAC state repository 112 and user registry 116 of FIG. 1. At step 204the users and permissions for each acquired role are specified.

Steps 206, 208 and 210 are provided to monitor the above condition (1),that is, to determine whether there are any valid and dormant users, andif so to analyze them. At step 206 each user identified at step 204 fora given role is analyzed, to decide if the user is a valid user. Forexample, the user's position in an associated organization, as shown byregistry 116 or the like, could be queried. The position information,together with pertinent RBAC policy, may then be used to indicatewhether the user is or is not a valid user for the given role. If so,the method proceeds to step 208, and otherwise, if the user is not avalid user, the method proceeds to step 210. At step 210 the user isremoved from the given role.

Step 208 of FIG. 2 is a decision step that determines if the user hasactivated the given role within a specified time interval. In order tomake this determination, information could be obtained from theappropriate event access log, such as an access log contained inrepository 110. Useful information from the log could include, forexample, data identifying the user and associated systems and actions,and timestamp information.

If it is determined at step 208 that the user has activated the givenrole at some time within the specified interval, the method of FIG. 2ends, without further action. However, if the user has not activated thegiven role within the interval, it is concluded that the user is adormant user. Accordingly, the method proceeds to step 210, and the useris removed from the given role.

Steps 212, 214 and 216 pertain to the above condition that a givenpermission granted to users of a role is superfluous or unnecessary forthat role. At step 212, rules pertaining to the pertinent RBAC policyare considered, in order to confirm that the given permission is validfor a particular user of the role. If step 212 is affirmative, themethod proceeds to step 214, and otherwise ends for the particular user.

Step 214 of FIG. 2 is a decision step that determines if at least aprespecified minimum number of activations of the given permission haveoccurred within a prespecified time. The minimum number could be onlyone. In order to make this determination, information is usefullyobtained from the appropriate event access log, such as an access logcontained in repository 110. Useful information from the log wouldinclude, for example, data identifying users and associated systems andactions, and timestamp information.

If it is determined at step 214 that at least the minimum number of useractivated permissions have occurred within the prespecified interval,the method of FIG. 2 ends, without further action. However, if at leastthe minimum number of activations have not occurred, it is determinedthat the given permission is a superfluous permission. Accordingly, themethod proceeds to step 216, and the given permission is removed fromthe role.

Referring further to FIG. 2, at step 218 the rules for RBAC policypertaining to each respective role is checked or considered, in regardto condition (3) pertaining to role size, and to condition (4)pertaining to dormant roles. Decision step 220 then queries whether thesize of a given role exceeds either a prespecified upper bound or lowerbound. If not, the method of FIG. 2 ends, and no further action is takenwith respect to the given role. If either bound is exceeded, the methodproceeds to step 222. At this step, action is taken, such as to alert asystem administrator to the situation, or to remove the given role as atool for accessing respective systems.

Step 224 is provided to determine whether a given role has become adormant role. More particularly, step 224 queries whether any user hasused the given role during a prespecified time interval. If the answerto this query is affirmative, the method of FIG. 2 ends, and no furtheraction is taken with respect to the given role. If the answer isnegative, the given role is considered to be dormant, and the methodproceeds to step 226. At this step, action is taken, such as to alert asystem administrator to the situation, or to remove the given role as atool for accessing respective systems.

It is anticipated that monitoring and adjustment steps of FIG. 2pertaining to the conditions (1)-(4), respectively, can each be carriedout at predetermined intervals of time which may be periodic, or may beaperiodic. By doing this, the status and conditions of respective roleswill be continually monitored over time. This will enable changed roleconditions to be detected and then responded to, with minimal delay.This, in turn, will enhance system security.

Referring to FIG. 3, there is shown a flowchart directed to assessingthe conditions (5)-(7) described above, in connection with a systemusing a particular RBAC policy for assessing security, and forimplementing corrections found to be necessary. FIG. 3 also shows stepsfor monitoring the system to detect a condition wherein two rolesoverlap. Steps of FIG. 3 may be carried out by ROMM 102 and othercomponents of system 100, in like manner with FIG. 2, but embodiments ofthe invention are not limited thereto.

Upon starting the method of FIG. 3, information pertaining to each ofthe roles of the particular RBAC policy is acquired at step 302. Suchinformation could, for example, be obtained by ROMM 102 by accessingRBAC state repository 112 and policy repository 118 of FIG. 1.

Steps 304, 306 and 308 are provided to monitor the above condition (5),pertaining to role risk, and to take any action required. At step 304,the method of FIG. 3 computes role risk level. More particularly, foreach role the sensitivity level of each permission of the role isevaluated. Each evaluated permission is then rated to be either of highsensitivity or low sensitivity.

At decision step 306, it is determined whether or not a role includesboth highly sensitive and low sensitive permissions. If not, the methodends. Otherwise, the method proceeds to step 308, wherein the highlysensitive permissions are grouped into a role which is separated fromthe role that includes all of the low sensitive permissions.

Steps 310, 312 and 314 monitor role concurrency at prespecifiedintervals, to detect any violations in regard thereto. Role concurrencyrefers to session events, wherein two or more users included in a givenrole each accesses the same system or resource at the same time.Accordingly, at each prespecified monitoring interval informationcontained in access log repository 110 or the like is accessed at step310. The accessed information is then used to identify each roleconcurrency session that has occurred since the last monitoringinterval.

At decision step 312, a query is made to determine whether the number ofidentified concurrency sessions has exceeded the maximum number of suchsessions permitted by the pertinent RBAC policy. If not, the methodends. However, if the query of decision step 312 is positive the methodproceeds to step 314, which takes certain action. One action would be toissue an alert of the situation to the system administrator. Anotheraction would be to split the given role into multiple roles, so thateach of such roles would have fewer users. This would act to reduce thenumber of concurrency sessions that would occur thereafter.

Steps 316, 318 and 320 pertain to the above condition (7), regardingpermission-based separation of duties. At step 316, RBAC policy isanalyzed to identify certain types of duties which require separationfrom other types of duties. Clearly, a user having a set of permissionsto perform duties of the first type should not also have a set ofpermissions to perform duties of the second type. Accordingly, decisionstep 318 determines whether or not there are any users in a given rolewho have access to mutually exclusive permissions. If not, the methodends. Otherwise, the method proceeds to step 320, to issue an alert tothe system administrator.

Steps 322 and 324 are directed to the condition of overlapping roles.Roles overlap one another if they both grant the same permissions to thesame users. At predetermined time intervals, step 322 determines whetheror not this condition exists. If not, the method ends. Otherwise, themethod proceeds to step 324, wherein role permissions are selectivelyregrouped, in order to discontinue the overlap condition.

It is anticipated that monitoring and adjustment steps of FIG. 3pertaining to respective conditions thereof can each be carried out atpredetermined intervals of time, which may be periodic, or may beaperiodic. By doing this, the status and conditions of respective roleswill be continually monitored over time. This will enable changed roleconditions to be detected and then responded to, with minimal delay.This, in turn, will enhance system security.

Referring to FIG. 4, there is shown ROMM 102 in further detail. ROMM 102includes a data access layer that has a query interface 402, wherein theinterface 402 is connected to exchange data with statistics database114, RBAC repository 112, user registry 116, and access log repository110. The data access layer of ROMM 102 further includes an eventinterface 404, connected to exchange data with access log repository110. Thus, the data access layer is configured to support query models,and also event flow models such as playback.

Each analysis function carried out by ROMM 102 is usefully implementedin a separate analysis module. Respective modules may be plugged intothe data access layer, to support a variety of analysis components.Also, new analysis modules can easily be added to the system. FIG. 4shows exemplary analysis modules 406, 408 and 410, which arerespectively connected to interfaces 402 and 404 as shown. Analysismodule 406 pertains to the unused permissions condition, analysis module408 pertains to inactive users, and analysis module 410 pertains to roleconcurrency.

In carrying out role analysis in regard to certain conditions of thetype described above, ROMM 102 enumerates all of such roles and visitseach one. Each pertinent analysis module is invoked during the visit,and role relationships are visible to the modules. Role analysis isusefully employed to analyze conditions such as role size, dormant usersand unused permissions, as described above in connection with FIG. 2.

For event analysis, analysis modules subscribe to the flow of events.More particularly, events stored in access log repository 110 are playedback through the event analysis modules. Event playback enablesobservation of dynamic runtime properties, which can be used to detectrole concurrency and dynamic separation of duty violations. Detectingrole concurrency enables concurrency parameters to be tuned to the mostoptimal levels. Unwanted concurrent role activations can also bedetected, so that appropriate action may be taken.

Referring to FIG. 5, there is shown a hierarchy of roles, which is afeature or characteristic of an RBAC control arrangement. FIG. 5 moreparticularly shows a number of exemplary users, or user positions502-522, of respective types that are common to business and otherorganizations. Each user or user position 502-522 could refer to aparticular function, or to a person tasked to carry out the particularfunction.

In accordance with RBAC, a role at one of the users of FIG. 5 could beacquired or inherited from a superior role. As an example, the role ofthe researcher 506 is shown to be inherited from the role of manager502. Thus, the manager role 502 is superior to the researcher role 506.

Moreover, a user or user position can inherit multiple roles. This isillustrated in FIG. 5 in connection with research IP 510. The user 510inherits a role from researcher 506, user 510 inherits a role fromresearcher 506, so that the role of user 506 is superior to (or a parentof) the role inherited by user 510. In addition, a user 510 inherits asecond role from a role of IP lawyer 518, which is thus superior to thesecond inherited role.

Referring further to FIG. 5, one or more permissions of a role may beassigned to or inherited by a user. As an example of this, FIG. 5 showsa permission assigned from the role of manager 502 to user 504. As afurther example, FIG. 5 shows a permission assigned from the role ofemployee 512 to user 520. The same or a different permission is alsoassigned from the role of employee 512 to user 522.

It is seen from the role hierarchy of FIG. 5 that the inheritance, ordistribution of roles and permissions, creates parent and childrelationships or classes. Before taking action to modify or improverestrictions on the role structure, in order to achieve roleoptimization, these parent and child classes need to be considered.

Referring to FIG. 6, there is shown a flowchart that illustrates analgorithm which may be used to automatically recognize dormant users ofa role, as referred to above in connection with condition (1), and toremove such users from the role. The algorithm of FIG. 6 is intended toautomatically remove only users who are directly assigned to the role,and to provide warning or notice of other cases.

At step 602, the user of a specified role is selected, wherein the roleis not an abstract role. At decision step 604, it is determined whetherthe user is or is not directly assigned to the specified role. If theuser is directly assigned the algorithm proceeds to step 606, andotherwise goes to step 608.

Step 606 determines the time D since the last activation of thespecified role by the selected user. In respective embodiments, D couldbe a date, or could be a specific date and time. At step 610, thealgorithm determines whether or not D is greater than a predeterminedperiod of time of maxUserAge. This is the maximum amount of time duringwhich a user may refrain from using the specified role, without becominga dormant user. Accordingly, if the determination at step 610 ispositive, the algorithm proceeds to step 612, and the selected user isremoved from the specified role. The algorithm then goes to step 614.

If the determination at step 610 is negative, the algorithm bypassesstep 612, and goes directly step 614. Thus, the selected user remainsassigned to the role. At step 614, it is decided whether or not thereare any more users of the specified role who should be selected forprocessing by the algorithm of FIG. 6. If not, the algorithm ends, andotherwise proceeds to step 616. Step 616 selects the next one of suchusers, and loops back to the input of step 604.

Step 608 provides notice that users are not assigned to the specifiedrole, in response to a negative output of step 604. The output 608 isdirected to the input of step 614.

Referring to FIG. 7, there is shown a flowchart that illustrates analgorithm which may be used to automatically recognize unusedpermissions, referred to above in connection with condition (2), and toremove such unused permissions from an associated role. The algorithm ofFIG. 7 is intended to automatically remove a permission from a givenrole that does not use the permission, only if all roles superior to thegiven role also do not use the permission.

At step 702, a specified role is selected that is not an abstract role.At step 704, all of the roles that are superior to the specified role,such as superior roles as described above, are identified.

Step 706 determines the time D since the last usage, of a selectedpermission granted by the specified role. In respective embodiments, Dcould be a date, or could be a specific date and time. At step 708 thealgorithm determines whether or not D is greater than a predeterminedperiod of time maxPermAge. This is the maximum time during which apermission can remain unused, without being considered to possibly besuperfluous.

If decision step 708 provides a negative result, the last usage time Dof the selected permission, in association with the specified role, iswithin the required time constraint. Accordingly, the algorithm proceedsto step 710, and the selected permission is kept. Step 710 performs afurther task, described hereinafter.

If the output of decision step 708 is positive, the last usage D of theselected permission exceeds the required constraint. In this case, thealgorithm proceeds to decision step 712, which determines whether thereare any roles to select that are superior to the specified role. If not,the algorithm proceeds to step 710, and otherwise goes to step 714 toselect one of the superior roles. The algorithm then proceeds to step716.

Step 716 determines D_(S), which is the time since the last usage of theselected permission, wherein the selected permission was granted by theselected superior role. At decision step 718, it is determined whetheror not D_(S) is greater than the time constraint maxPermAge. If theresult of decision step 718 is negative, the algorithm proceeds to step710, and the selected permission step is kept. Such result indicatesthat the selected permission has been used within the time constraint,for at least one role that is superior to the specified role.

If decision step 718 provides a positive result, the algorithm goes tostep 720, which determines whether there are any further superior rolesto select and consider. If there are, the algorithm returns to the inputof step 714, and selects the next superior role. The process of FIG. 7then continues, until a negative output is provided by either step 710or step 720.

It is to be appreciated that the output of step 720 will becomenegative, only if all last usage values D and D_(S) of the selectedpermission exceed the constraint maxPermAge. This situation indicatesthat the selected permission has been unused during the required timefor both the specified role and all roles superior thereto. Accordingly,the algorithm proceeds to step 722, and the selected permission isremoved from the specified role.

In addition to retaining the selected permission, step 710 also providesnotice of each condition were D and D_(S) for the selected permissionexceeds the constraint maxPermAge.

While not shown, the algorithm of FIG. 7 could be readily adapted toiteratively process each of multiple permissions, that are all grantedby the specified role.

FIG. 8 is a pictorial representation of a network of data processingsystems in which illustrative embodiments of the invention may beimplemented. Network data processing system 800 is a network ofcomputers in which the illustrative embodiments may be implemented.Network data processing system 800 contains network 802, which is themedium used to provide communications links between various devices andcomputers connected together within network data processing system 800.Network 802 may include connections, such as wire, wirelesscommunication links, or fiber optic cables.

In the depicted example, server computer 804 and server computer 806connect to network 802 along with storage unit 808. In addition, clientcomputers 810, 812, and 814 connect to network 802. Client computers810, 812, and 814 may be, for example, personal computers or networkcomputers. In the depicted example, server computer 804 providesinformation, such as boot files, operating system images, andapplications to client computers 810, 812, and 814. Client computers810, 812, and 814 are clients to server computer 804 in this example.Network data processing system 800 may include additional servercomputers, client computers, and other devices not shown.

Program code located in network data processing system 800 may be storedon a computer-recordable storage medium and downloaded to a dataprocessing system or other device for use. For example, program code maybe stored on a computer-recordable storage medium on server computer 804and downloaded to client computer 810 over network 802 for use on clientcomputer 810.

In the depicted example, network data processing system 800 is theInternet with network 802 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers consisting of thousands of commercial, governmental,educational and other computer systems that route data and messages. Ofcourse, network data processing system 800 also may be implemented as anumber of different types of networks, such as, for example, anintranet, a local area network (LAN), or a wide area network (WAN). FIG.8 is intended as an example, and not as an architectural limitation forthe different illustrative embodiments.

Turning now to FIG. 9, an illustration of a data processing system isdepicted in accordance with an illustrative embodiment. The dataprocessing system may be used as one or more of the components forsystem 800. In this illustrative example, data processing system 900includes communications fabric 902, which provides communicationsbetween processor unit 904, memory 906, persistent storage 908,communications unit 910, input/output (I/O) unit 912, and display 914.

Processor unit 904 serves to execute instructions for software that maybe loaded into memory 906. Processor unit 904 may be a number ofprocessors, a multi-processor core, or some other type of processor,depending on the particular implementation. A number, as used hereinwith reference to an item, means one or more items. Further, processorunit 904 may be implemented using a number of heterogeneous processorsystems in which a main processor is present with secondary processorson a single chip. As another illustrative example, processor unit 904may be a symmetric multi-processor system containing multiple processorsof the same type.

Memory 906 and persistent storage 908 are examples of storage devices916. A storage device is any piece of hardware that is capable ofstoring information, such as, for example, without limitation, data,program code in functional form, and/or other suitable informationeither on a temporary basis and/or a permanent basis. Storage devices916 may also be referred to as computer-readable storage devices inthese examples. Memory 906, in these examples, may be, for example, arandom access memory or any other suitable volatile or non-volatilestorage device. Persistent storage 908 may take various forms, dependingon the particular implementation.

For example, persistent storage 908 may contain one or more componentsor devices. For example, persistent storage 908 may be a hard drive, aflash memory, a rewritable optical disk, a rewritable magnetic tape, orsome combination of the above. The media used by persistent storage 908also may be removable. For example, a removable hard drive may be usedfor persistent storage 908.

Communications unit 910, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 910 is a network interface card. Communications unit910 may provide communications through the use of either or bothphysical and wireless communications links.

Input/output unit 912 allows for input and output of data with otherdevices that may be connected to data processing system 900. Forexample, input/output unit 912 may provide a connection for user inputthrough a keyboard, a mouse, and/or some other suitable input device.Further, input/output unit 912 may send output to a printer. Display 914provides a mechanism to display information to a user.

Instructions for the operating system, applications, and/or programs maybe located in storage devices 916, which are in communication withprocessor unit 904 through communications fabric 902. In theseillustrative examples, the instructions are in a functional form onpersistent storage 908. These instructions may be loaded into memory 906for execution by processor unit 904. The processes of the differentembodiments may be performed by processor unit 904 using computerimplemented instructions, which may be located in a memory, such asmemory 906.

These instructions are referred to as program code, computer-usableprogram code, or computer-readable program code that may be read andexecuted by a processor in processor unit 904. The program code in thedifferent embodiments may be embodied on different physical orcomputer-readable storage media, such as memory 906 or persistentstorage 908.

Program code 918 is located in a functional form on computer-readablemedia 920 that is selectively removable and may be loaded onto ortransferred to data processing system 900 for execution by processorunit 904. Program code 918 and computer-readable media 920 form computerprogram product 922 in these examples. In one example, computer-readablemedia 920 may be computer-readable storage media 924. Computer-readablestorage media 924 may include, for example, an optical or magnetic diskthat is inserted or placed into a drive or other device that is part ofpersistent storage 908 for transfer onto a storage device, such as ahard drive, that is part of persistent storage 908. Computer-readablestorage media 924 also may take the form of a persistent storage, suchas a hard drive, a thumb drive, or a flash memory, that is connected todata processing system 900. In some instances, computer-readable storagemedia 924 may not be removable from data processing system 900.

The different components illustrated for data processing system 900 arenot meant to provide architectural limitations to the manner in whichdifferent embodiments may be implemented. The different illustrativeembodiments may be implemented in a data processing system includingcomponents in addition to or in place of those illustrated for dataprocessing system 900. Other components shown in FIG. 9 can be variedfrom the illustrative examples shown. The different embodiments may beimplemented using any hardware device or system capable of runningprogram code. As one example, the data processing system may includeorganic components integrated with inorganic components and/or may becomprised entirely of organic components excluding a human being. Forexample, a storage device may be comprised of an organic semiconductor.

In another illustrative example, processor unit 904 may take the form ofa hardware unit that has circuits that are manufactured or configuredfor a particular use. This type of hardware may perform operationswithout needing program code to be loaded into a memory from a storagedevice to be configured to perform the operations.

For example, when processor unit 904 takes the form of a hardware unit,processor unit 904 may be a circuit system, an application specificintegrated circuit (ASIC), a programmable logic device, or some othersuitable type of hardware configured to perform a number of operations.With a programmable logic device, the device is configured to performthe number of operations. The device may be reconfigured at a later timeor may be permanently configured to perform the number of operations.Examples of programmable logic devices include, for example, aprogrammable logic array, programmable array logic, a field programmablelogic array, a field programmable gate array, and other suitablehardware devices. With this type of implementation, program code 918 maybe omitted because the processes for the different embodiments areimplemented in a hardware unit.

In still another illustrative example, processor unit 904 may beimplemented using a combination of processors found in computers andhardware units. Processor unit 904 may have a number of hardware unitsand a number of processors that are configured to run program code 918.With this depicted example, some of the processes may be implemented inthe number of hardware units, while other processes may be implementedin the number of processors.

As another example, a storage device in data processing system 900 isany hardware apparatus that may store data. Memory 906, persistentstorage 908, and computer-readable media 920 are examples of storagedevices in a tangible form.

In another example, a bus system may be used to implement communicationsfabric 902 and may be comprised of one or more buses, such as a systembus or an input/output bus. Of course, the bus system may be implementedusing any suitable type of architecture that provides for a transfer ofdata between different components or devices attached to the bus system.Additionally, a communications unit may include one or more devices usedto transmit and receive data, such as a modem or a network adapter.Further, a memory may be, for example, memory 906, or a cache, such asfound in an interface and memory controller hub that may be present incommunications fabric 902.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiment. The terminology used herein was chosen to best explain theprinciples of the embodiment, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed here.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

1. In association with a computer system wherein a specified rolecontrols user access, the specified role comprises one or more users andone or more permissions, and a set of prespecified rules pertains to thespecified role, a computer implemented method comprising the steps of:recording access data pertaining to each of a succession of accessevents in an access log, wherein each event comprises an instance of thecomputer system being accessed by a particular user; analyzing recordeddata contained in the access log at selected time intervals, in order todetect one of a plurality of prespecified conditions; responsive todetecting a prespecified condition, selectively determining whether anychange to the users or to the permissions of the specified role isneeded; and implementing each needed change to the users or to thepermissions.
 2. The method of claim 1, wherein: the specified role isone of multiple roles that are respectively provided to control accessto the computer system, wherein each role is provided in accordance witha role based access control (RBAC) policy.
 3. The method of claim 1,wherein: responsive to analyzing specified access data contained in theaccess log that pertains to a specified user, detecting a condition thatthe specified user is a dormant user, and then removing the specifieduser from the specified role.
 4. The method of claim 3, wherein: thespecified access data includes information showing that the time sincethe last activation of the specified role by the specified user isgreater than a predetermined time limit.
 5. The method of claim 1,wherein: responsive to analyzing specified access data contained in theaccess log that pertains to a specified permission granted by thespecified role, detecting a condition that the time since the last useof the specified permission, in association with the specified role, isgreater than a predetermined time limit, whereupon the specifiedpermission is removed from the specified role.
 6. The method of claim 5,wherein: the specified permission is granted by one or more roles thatare each superior to the specified role, the specified access data isused to compute, for each superior role, the time since the last use ofthe specified permission granted by that superior role, and it isdetermined that the computed times for all of the superior roles arerespectively greater than the predetermined time limit.
 7. The method ofclaim 1, wherein: responsive to analyzing access data contained in theaccess log, and detecting a condition that the time since any user hasactivated the specified role exceeds a predetermined time limit, thespecified role is discontinued.
 8. The method of claim 1, wherein:recorded data contained in the access log is analyzed to detect acondition selected from a group consisting of role size, role risk, roleconcurrency, permission-based separation of duties, and overlappingroles.
 9. The method of claim 8, wherein: responsive to detecting acondition of role risk, permissions determined to be of a highsensitivity are placed in a role different from a role containingpermissions that are determined to be of a low sensitivity.
 10. Themethod of claim 1, wherein: analyzing recorded data contained in theaccess log includes operating a role monitoring component that isprovided with a data access layer having a query interface and an eventflow interface.
 11. The method of claim 10, wherein: one or moreanalysis modules are each plugged into the data access layer, to supportanalysis for a selected corresponding condition.
 12. The method of claim11, wherein: events recorded in the access log are respectively playedback through an event analysis module, to detect one or more specifiedtypes of conditions.
 13. The method of claim 11, wherein: a differentanalysis module is provided for use in detecting each of a plurality ofprespecified conditions, including at least superfluous permissions,dormant users, and role concurrency.
 14. The method of claim 1, wherein:the selected time intervals comprise periodic time intervals oraperiodic time intervals, selectively.
 15. The method of claim 1,wherein: the specified role enables a user to access each one ofmultiple computer systems. 16-25. (canceled)